This ZIP file contains an update to the MOMI server - Version 5.62

This server is:

   - based on version 5.61

   - compatible with MOMI PC Clients: 5.80 to 5.93


Sections
---------

   Changes in this update
   How to update
   Vproc information


Changes in this update
----------------------

- Removed collection of CPUs_physical, item code ZSYS^VAL^CINF^CPU^PHYSCOUNT
  (82) from call to PROCESSOR_GETINFOLIST_ issued, by default, every 10
  seconds, from the MOMI CPU Collector (one per processor) due to excessive
  wall clock time usage. This value is not currently output by the client.
  Customer reported that this item code results in an I/O to $YMIOP.

- Corrected a condition where under certain situations an unusable file to the
  spooler remained open after processing a spooler job copy request and an
  error was encountered. The MOMI server would usually automatically stop but
  the file opens could accumulate if the user performed multiple retries.


How to update
-------------

Download the ZIP file to your PC, right-click on it and select Extract All...
 (i.e. using the Windows built-in extractor) and follow the prompts.
 Double-click on MOMIFTP.exe to launch the transfer utility or manually
 transfer the files.


If using MOMIFTP ->

   1) in the extracted file double-click on MOMIFTP, follow the on-screen
      instructions and leave the default of "Update Installation". This utility
      is the same one used in our full release package but contains just the
      updated files and expects an installation is already present. MOMIFTP
      transfers files in the correct manner (i.e. ASCII or binary), set file
      code, and performs file rename of an existing file automatically (i.e. 2
      for oldest, 1 for next oldest). You can run MOMIFTP while $MOMI is
      operating on your NonStop System.

   2) continue with step 5 below.


If using another file transfer method, follow the steps below but you need only
 transfer the MOMI suitable for your platform ->

   1) On the NonStop System, volume to the location where the MOMI server is
      installed.

   2) To prepare to receive the new object file, the existing file needs to be
      renamed.  The rename convention we use places a number at the end of the
      file name and the highest number is the oldest.  Purge the oldest BWMOMI?
      object and rename the others:

         TNS/X    purge  bwmomix2
                  rename bwmomix1,bwmomix2
                  rename bwmomix ,bwmomix1

         TNS/E    purge  bwmomii2
                  rename bwmomii1,bwmomii2
                  rename bwmomii ,bwmomii1

         TNS/R    purge  bwmomi2
                  rename bwmomi1,bwmomi2
                  rename bwmomi ,bwmomi1

   3) Using your favorite file transfer utility copy the needed files as shown
       below from your PC to the NonStop System in the manner indicated:

         - BINARY the BWMOMIx
         - BINARY the BWMOMIi
         - BINARY the BWMOMI

   4) On the NonStop System, alter the file code:

         fup alter bwmomix,code 500
         fup alter bwmomii,code 800
         fup alter bwmomi ,code 700

-> 5) SQL compile the object file with the TACL obey file:

         obey obycsql

   6) if MOMI is not running under a Super.Group, also update BWSSG (see below).

   7) restart MOMI with the TACL obey file:

         obey obymomi


If MOMI is started under Super.Super or a "Super.Group", skip this section as
 BWSSG is not needed (i.e. MOMI has the security it needs). Starting MOMI under
 any other ID means that BWSSG should be created (and secured as indicated
 below) to indirectly give MOMI the ability to perform PING, Trace Route and
 System time maintenance (the steps below omit logon to the super.* id):

         Purge  BWSSG2

         Rename BWSSG1, BWSSG2

         Rename BWSSG, BWSSG1

         FUP DUP BWMOMI, BWSSG,sourcedate (BWMOMIi on TNS/E - BWMOMIx on TNS/X)

         FUP GIVE BWSSG, <super.group>    (where <super.group> your desired ID)

         FUP SECURE BWSSG,NGNG,PROGID




Vproc information
-----------------

BWMOMIX
     Binder timestamp:  12AUG2019 17:55:11 LCT, 12AUG2019 23:55:11 GMT
    Version procedure:  T8432L01_01OCT2014_CCPXMAIN_O1
    Version procedure:  T0000G06___OSS01SC__2017_05_03
    Version procedure:  T0000G06___V5_62____2019_08_12
    Version procedure:  T0000G06___TOMCYAP__2014_10_24
    Version procedure:  T0000G06___TDS01LT__2017_08_29
    Version procedure:  T0000G06___UTL02LT__2017_07_27
    TNS/X Native Mode:  runnable file

BWMOMII
     Binder timestamp:  12AUG2019 17:46:43 LCT, 12AUG2019 23:46:43 GMT
    Version procedure:  T0000G06___OSS01SC__2017_05_03
    Version procedure:  T0000G06___V5_62____2019_08_12
    Version procedure:  T8432H04_26FEB2014_CCPLMAIN
    Version procedure:  T0000G06___TOMCYAP__2014_10_24
    Version procedure:  T0000G06___TDS01LT__2017_08_29
    Version procedure:  T0000G06___UTL02LT__2017_07_27
    TNS/E Native Mode:  runnable file

BWMOMI
 GMT Binder timestamp:  12AUG2019 23:45:53
    Version procedure:  T0000G06___V5_62____2019_08_12
    Version procedure:  T8432G10_10MAY2007_CRTLMAIN_ABL
    Version procedure:  T0000G06_S_OSS01SC__2017_05_03
    Version procedure:  T0000G06___TOMCYAP__2014_10_24
    Version procedure:  T0000G06___TDS01LT__2017_08_29
    Version procedure:  T0000G06___UTL02LT__2017_07_27
          Native Mode:  runnable file